<html>
    <head>
        <meta http-equiv="Content-type" content="text/html; charset=utf-8"/>
        <title>2. Miscellaneous</title>
        <link rel="stylesheet" href="../css/main.css" type="text/css" media="screen" title="Ref" charset="utf-8"/>
    </head>
    <body class="body">
    <h1><a name="2. Miscellaneous">2. Miscellaneous</a></h1>
<h2><a name="2.1 Bootstrap Classes">2.1 Bootstrap Classes</a></h2><a href="http://www.grails.org/Bootstrap%20Classes" target="blank">Grails Bootstrap Classes</a> are also supported by the plugin.<h2><a name="2.2 Participation in install-templates">2.2 Participation in install-templates</a></h2>The plugin will participate in <a href="http://grails.org/doc/latest/ref/Command%20Line/install-templates.html." target="blank">grails install-templates</a><p class="paragraph"/>A set of templates will be installed at src/templates/batch directory. Please, refer to <a href="../ref/Command Line/batch-war.html" class="Command Line">batch-war</a> to know how these templates will be handled.
<h2><a name="2.3. Logging">2.3. Logging</a></h2>You can enable bootstrap activity logging using the namespace 'org.grails.plugin.batch'.<p class="paragraph"/>For more information about Grails logging, please consult: <a href="http://grails.org/doc/latest/guide/3.%20Configuration.html#3.1.2%20Logging" target="blank">Grails Logging</a><p class="paragraph"/><blockquote class="warning">
Be aware that log4j is initialized after some other steps. If you want debug information from Bootstrap before log4j kick in, use <code>grails.plugins.batch.debugLauncher</code> system property.
</blockquote>

    </body>
</html>
